docs: add RELEASING.md#29
Merged
Merged
Conversation
Document the manual release process so any maintainer can cut a release without needing to ask. Linked from the README. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
bm1549
added
documentation
bengl
requested changes
May 8, 2026
|
|
||
| - Push access to `main` on this repository. | ||
| - The [`gh`](https://cli.github.com/) CLI, authenticated against `DataDog/dc-polyfill`. | ||
| - Logged in to an npm account with publish access to `dc-polyfill`. Check with `npm whoami`; run `npm login` if needed. If you don't have publish access, ask an existing maintainer. |
Contributor
There was a problem hiding this comment.
Logged in to the npm account.
bm1549
commented
May 8, 2026
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
bm1549
commented
May 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
RELEASING.mddocumenting the manual release process (prereqs, release commands, verification).README.mdunder a new "Releasing" section.The runbook publishes to npm before pushing the version tag so a failed
npm publishdoesn't leave the repo advertising a tag that points at no published version, and includesnpm publish --dry-runas a sanity check before the real publish.Test plan
RELEASING.mdagainst the repo's actual release pattern (npm-published versions match0.1.Xcommits +v0.1.Xtags).npm paack --dry-runto confirm REALEASING.md is not included, although README.md is still present (NPM does this)🤖 Generated with Claude Code